Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Previous Next

DAOS read only


I have enabled DAOS and compacted the mailfiles using compact -c -daos on.
After the compact has successfully finished, I saw that DAOS state was READ/WRITE on all files.
Today some (3 of 400) databases have a DAOS state of READONLY.
Can anyone explain what causes the change? What are the effects when the state is READONLY?


A database can have one of three DAOS states

Disabled - the database does not have any objects in DAOS and it will not store objects in DAOS
Read/Write - the database is DAOS enabled, any qualifying new objects will go into DAOS
Read Only - the database has DAOS objects and those will continue to work fine, but new objects will be written into the NSF and not DAOS because the database does not meet the criteria for using DAOS (we need to figure out what would cause this )

A database can only participate in DAOS if these criteria are met
1) the system is transaction logged
2) DAOS is enables at the server level

I assume you meet these two criteria, you can verify this by issuing a
SHOW SERVER console command
you should see
DAOS: Enabled


3) the individual database is transaction logged
4) the individual database has the DAOS property set
5) the database is ODS 51

to check this, run a
SHOW DIR directory_or_file_name

for example

> sh dir zzz
DbName                                Version Log  DAOS  ---Modified Time----
C:\Lotus\Domino\data\zzz\zmarx.nsf     V8:51  Yes   Yes  03/18/2009 07:56:24 AM
C:\Lotus\Domino\data\zzz\showard.nsf   V8:51  Yes   No   03/12/2009 07:30:15 AM
C:\Lotus\Domino\data\zzz\pcastor.nsf   V8:51  No    No   03/12/2009 07:29:54 AM
C:\Lotus\Domino\data\zzz\mhoward.nsf   V8:51  Yes   No   03/12/2009 07:30:12 AM
C:\Lotus\Domino\data\zzz\lfine.nsf     V8:51  Yes   No   03/12/2009 07:30:08 AM
C:\Lotus\Domino\data\zzz\jpollax.nsf   V8:51  No    No   03/12/2009 07:29:51 AM
C:\Lotus\Domino\data\zzz\hmarx.nsf     V8:51  Yes   No   03/12/2009 07:30:05 AM
C:\Lotus\Domino\data\zzz\groucho.nsf   V8:51  Yes   Yes  03/18/2009 07:55:49 AM
C:\Lotus\Domino\data\zzz\gmarx.nsf     V8:51  Yes   Yes  03/18/2009 07:56:02 AM
C:\Lotus\Domino\data\zzz\cmarx.nsf     V8:51  Yes   Yes  03/18/2009 07:56:10 AM
C:\Lotus\Domino\data\zzz\choward.nsf   V8:51  Yes   No   03/12/2009 07:29:08 AM
C:\Lotus\Domino\data\zzz\cderita.nsf   V8:51  Yes   No   03/12/2009 07:29:57 AM
Total files: 12

For the files in question, verify that ODS version is V8:51, Logging is Yes and DAOS is Yes.

Are any of these indicators wrong for your Read/Write databases ????? (if so, then the next step is to determine how/why)



Feedback response number GRHE7Q9FMS created by ~Sean Ekresaski on 03/18/2009

DAOS state:READONLY (~Dean Quettoote... 18.Mar.09)
. . DAOS read only (~Denise Zenpone... 18.Mar.09)
. . . . Since they were at one point READ/W... (~James Reveluly... 18.Mar.09)
. . . . Points 1- 5 = OK (~Dean Quettoote... 19.Mar.09)
. . . . . . what does SHOW DIR display for thes... (~Denise Zenpone... 19.Mar.09)
. . . . . . . . unfortunately ... (~Dean Quettoote... 19.Mar.09)




Printer-friendly

Search this forum

Member Tools


RSS Feeds

 RSS feedsRSS
All forum posts RSS
All main topics RSS